fix(cache): record audit scope and reject mismatched cache reads (#542) - #549

Addressed.

1. expected_level=3 passed. _run_baseline_checks defaults to level=3, so accepting a level-1 cache would have remediated against a narrower audit than the one it would otherwise run
2. Added a filtered boolean to the envelope rather than the control-ID set, --include/--exclude can't be expressed as a tag string, and a set would make the envelope large and the comparison brittle. run_sieve_audit has no profile parameter (that filtering happens in the MCP tool), so profile isn't covered here
3. Both done. A filtered audit now writes under its own cache key, so it can't replace the unfiltered entry but repeat filtered runs still hit. Remediation resolves [stores.cache] via _load_merged_stores + resolve_stores and reproduces the same key derivation as tools/audit.py. Kept "Fixes Remediation trusts the audit cache regardless of framework, level, or tag filter #542".
4. CACHE_VERSION 1 → 2, and the check is now != CACHE_VERSION rather than > — the old upper-bound form would still have read a v1 envelope, which has no tags/filtered keys and would present a possibly filtered audit as unfiltered.
5. framework-design.md 10.4 gains two requirements: the envelope's scope fields plus the distinct key for filtered runs, and the scoped-read semantics including the version rule. The remediation requirement now also states the store it reads through.
6. Trailer is `Assisted-by: Claude:claude-opus-4-5.

Tests: 38 in test_audit_cache.py (7 new across two classes), tests/darnit_baseline 900 passed, tests/darnit minus parity 2053 passed.

Three failures in the long tests/darnit run — test_mcp_equals_direct_equals_cli, TestProgressLines::test_progress_lines_use_n_over_m_counter, TestSecretRedaction::test_leaked_exception_message_does_not_reach_report, all pass individually and fail only under a full-suite run. I checked test_mcp_equals_direct_equals_cli against the unmodified lockfile and it fails identically there, so they're pre-existing. Probably worth their own issue.

I also left ruff format alone on cli.py and orchestrator.py: running it there reformats ~180 lines I didn't touch (171 files in the repo currently fail format --check), which seemed like a separate PR.

Rebuilt on current main and force-pushed (one commit). Main had rewritten the three conflicting files, so I re-applied the change instead of resolving the conflicts in place.

1. Store loading and the cache key. Remediation now reads through read_full_audit_cache() in tools/audit.py. It resolves the operator configuration the way run_sieve_audit does, calls _load_merged_stores(framework_name, operator) with the new signature, and closes the bundle. The key comes from one helper, audit_cache_key(), used by the writer and the reader.
2. Profile-filtered audits fail closed. run_sieve_audit records an audit as filtered when it has tags, when the caller says so, or when the caller passed controls without saying. The Baseline tool passes cache_filtered=bool(profile), the CLI computes it from --tags/--include/--exclude, and the generic MCP audit tool states cache_filtered=False. Profile test: tests/darnit_baseline/test_audit_cache_scope.py.

Checked through the CLI on a committed one-file repository:

One existing test changed: test_run_sieve_audit_without_cache_write passes its own controls, so it now states cache_filtered=False.

Full suite: 5167 passed, 19 skipped. The three tests that failed for me before did not fail.

Note for #576: it wires --profile into darnit audit. Whichever of the two merges second should add args.profile to the CLI's cache_filtered.

Drafted with Claude; reviewed and posted by me.

@mlieberman85 the Oct 12 points, rebased onto main:

1. Configured store: invalidate_full_audit_cache() resolves the same store and key as the read, and both call sites use it. New test writes to a local-fs store, shows the old call leaving it in place, and the new one expiring it. Spec 10.4 updated.
2. PR body: rewritten, with the AI tool named.
3. cache_filtered: the CLI now compares the control count after filtering with the loaded count. --profile from fix(cli): make darnit audit --profile filter the controls #576 is covered without changes there.
4. Simpler: filtered audits are not written at all. The -filtered key and the tags/filtered fields are gone. The profile test runs the real audit_openssf_baseline() and asserts read_full_audit_cache() is None.

5173 tests pass.